It's the same thing here in iOS 18, some Artwork provides colors, and some does not. // log.debug("👀 album: \(album.title) \(album.releaseDate)"), album is instance of Album // log.debug("👀 artwork.backgroundColor: \(color.description)"), artwork is instance of Artwork [🤖] 👀 album: Ms. Salazar Optional(2025-02-21 12:00:00 +0000) [🤖] 👀 color is nil! [🤖] 👀 album: Built Different Optional(2025-03-14 12:00:00 +0000) [🤖] 👀 color is nil! [🤖] 👀 album: More Leaks Optional(2025-03-07 12:00:00 +0000) [🤖] 👀 color is nil! [🤖] 👀 album: Caviar nil [🤖] 👀 color is nil! [🤖] 👀 album: Cruel Joke nil [🤖] 👀 color is nil! [🤖] 👀 album: Choses Sauvages III nil [🤖] 👀 color is nil! [🤖] 👀 album: After the Last Sky nil [🤖] 👀 color is nil! [🤖] 👀 album: Laini Tani nil [🤖] 👀 color is nil! [🤖] 👀 album: Horse Meat Disco Presents Disco & Boogie From Brazil, Vol. 1 nil [🤖] 👀 color is nil! [🤖] 👀 album: Even In Arcadia Optional(2025-03-13 12:00:00 +0000) [🤖] 👀 color is nil! [🤖] 👀 album: IC-02 Bogotá nil [🤖] 👀 color is nil! [🤖] 👀 album: Articulate Excuses Optional(2025-03-14 12:00:00 +0000) [🤖] 👀 color is nil! [🤖] 👀 album: SABLE, fABLE Optional(2025-03-14 07:00:00 +0000) [🤖] 👀 color: UIExtendedSRGBColorSpace 0.941176 0.603922 0.521569 1 [🤖] 👀 album: THE NAVY ALBUM nil [🤖] 👀 color: UIExtendedSRGBColorSpace 0 0.0352941 0.188235 1 [🤖] 👀 album: Plæygirl nil [🤖] 👀 color is nil! Do I need to do something to get the colors?

same here! i think custom image works in previous beta, like 1 or 2. but recently it does not work anymore.

After set my debug target to iOS 17, i can install my app to my device now.

after upgrading to Xcode 15, I had the same error when building. however, after checking my build phase, it turned out the run script was not the last step. so I move the run script to the bottom, then it compiles successfully. it might not suit your situation, post so it may be helpful for others.

Related discussion: Live Activity update not working while AVAudioSessionCategoryPlayback in backgroud Changing the live activity without push notification iOS 16 Live Activities cann't be refreshed in the background ? Update live activity without push notifications and with the app in background

The RC still does not fix this issue, we removed all the usage of this API.

Every developer team who meet this issue should open a feedback, I hope the number of feedbacks will raise the importance of this issue.

Hi, we have the same issue, nearly before the release, we realize that we need to request permission to use the Family Control entitlement. Can you share how long will it take to get the results of this request?

Same issue here. I submit a feedback: FB11366424 (iOS 16.0 beta 7: Text(Date(), style: .timer) does not update in Widget) Hope it is a bug and will get fixed soon!

Same issue, same thoughts. I can get apps name in the shield extension, but can't get apps name in the report extension. Also in the report extension, I can get the name of categories, and it has the same requirement, so can't get apps name looks like a bug for me. Also in the WWDC session video, the screenshot of WorkLog demo shows screen time per app, so I think we should be able to do the same thing in our own app. I'm using beta 3 and waiting for beta 4.

Xcode 13.3 fixed this. Hooray~!

Hi, we're developing rating features as well. but we found we can hardly make the rating for songs sync between our app and Apple Music, can you share which API are you using? that will help us a lot! thanks.

Sorry, don't know how to edit my question. I only check Intent is eligible for widgets in intent definition file.

Unable to find the edit button, I'll attach more logs here. Debug with: Xcode 13.0 beta 5 (13A5212g) iOS 15 beta 7 2021-08-27 16:23:51.202825+0800 MyApp[431:12260] [xpc.exceptions] <NSXPCConnection: 0x282a6f2a0> connection to service with pid 129 named com.apple.cloudd: Exception caught during invocation of reply block to message 'fetchLongLivedOperationsWithIDs:completionHandler:'. Exception: CKDatabaseOperations must be submitted to a CKDatabase ( 0   CoreFoundation                      0x00000001820db070 556693B0-3E65-30B3-B026-7107FD29DC41 + 626800 1   libobjc.A.dylib                     0x000000019a58df64 objc_exception_throw + 60 2   CloudKit                            0x000000018948c1b4 CKStringFromApplicationPermissionStatus + 6784 3   CloudKit                            0x0000000189495e6c CKStringFromApplicationPermissionStatus + 46904 4   OffScreenKit                        0x00000001070753d0 $s8IceCream15DatabaseManagerPAAE34resumeLongLivedOperationIfPossibleyyFySaySSGSg_s5Error_pSgtcfU_ySo11CKOperationCSg_AHtcfU_ + 536 5   libswiftCloudKit.dylib              0x000000019fe60760 0F47946A-53BB-344F-ABC5-228D48BAE29F + 100192 6   CloudKit                            0x0000000189494098 CKStringFromApplicationPermissionStatus + 39268 7   CloudKit                            0x00000001894939d4 CKStringFromApplicationPermissionStatus + 37536 8   CoreFoundation                      0x0000000182064304 556693B0-3E65-30B3-B026-7107FD29DC41 + 140036 9   CoreFoundation                      0x0000000182081ad4 556693B0-3E65-30B3-B026-7107FD29DC41 + 260820 10  Foundation                          0x00000001838a1930 AD55BAA6-3C1C-3392-AFBC-73E9063C34B9 + 219440 11  Foundation                          0x00000001838c2828 AD55BAA6-3C1C-3392-AFBC-73E9063C34B9 + 354344 12  Foundation                          0x000000018389d4b4 AD55BAA6-3C1C-3392-AFBC-73E9063C34B9 + 201908 13  libxpc.dylib                        0x00000001f216732c A519A4A5-9D87-3B62-9585-41EDADDD5127 + 115500 14  libxpc.dylib                        0x00000001f215a85c A519A4A5-9D87-3B62-9585-41EDADDD5127 + 63580 15  libdispatch.dylib                   0x0000000181d4d9d0 70FBC63E-C446-3BD3-A3BD-6F022317469B + 14800 16  libdispatch.dylib                   0x0000000181d6afd4 70FBC63E-C446-3BD3-A3BD-6F022317469B + 135124 17  libdispatch.dylib                   0x0000000181d54f84 70FBC63E-C446-3BD3-A3BD-6F022317469B + 44932 18  libdispatch.dylib                   0x0000000181d55c44 70FBC63E-C446-3BD3-A3BD-6F022317469B + 48196 19  libdispatch.dylib                   0x0000000181d60318 70FBC63E-C446-3BD3-A3BD-6F022317469B + 90904 20  libsystem_pthread.dylib             0x00000001f21311b0 _pthread_wqthread + 288 21  libsystem_pthread.dylib             0x00000001f2130f50 start_wqthread + 8 )

Yes, when my iOS app running on Mac, it feels it's running on iPad, so the verify logic should be the same process on iOS. I think the receipt provided by Mac App Store should make some changes, let's wait for the next release of macOS.